API

System APIs

POST system/rambase-event-types

This resource creates new RamBase event types without parameters.

HTTP method POST
URI https://api.rambase.net/system/rambase-event-types
Supported formats Xml, Html, Json (ex. $format=json)
Successful HTTP status code 201
API resource identifier 255, version 35

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
<RamBaseEventType>
2
     <Key
Key

Required/mandatory field

Key of the Event Type. This key will be used to identify which event to fire.

Input must match the following regular expression pattern: ^([A-Za-z0-9_-]+)$

>
{String}</Key>
3
     <Description
Description

Description of the Event Type

This field is optional.

>
{String}</Description>
4
     <AllowWebhooks
AllowWebhooks

If the Event Type can be used to create webhooks

Default value: False

This field is optional.

>
{Boolean}</AllowWebhooks>
5
     <AllowAutomatedFlows
AllowAutomatedFlows

Whether this event type can be used in an automated flow.

Default value: False

This field is optional.

>
{Boolean}</AllowAutomatedFlows>
6
     <Name
Name

Required/mandatory field

Name of the rambase event type. This should be more human readable than eventtype.

>
{String}</Name>
7
     <Namespace
Namespace

Namespace of the rambase event type

This field is optional.

>
{String}</Namespace>
8
     <ObjectDetailsUri
ObjectDetailsUri

API location for where to find more information about the object this event occurred for. May contains placeholders from with reference to parameter names. The parameter names are case sensitive.

This field is optional.

>
{String}</ObjectDetailsUri>
9
</RamBaseEventType>
1
{
2
     "ramBaseEventType": {
3
          "key
Key

Required/mandatory field

Key of the Event Type. This key will be used to identify which event to fire.

Input must match the following regular expression pattern: ^([A-Za-z0-9_-]+)$

":
"{String}",
4
          "description
Description

Description of the Event Type

This field is optional.

":
"{String}",
5
          "allowWebhooks
AllowWebhooks

If the Event Type can be used to create webhooks

Default value: False

This field is optional.

":
"{Boolean}",
6
          "allowAutomatedFlows
AllowAutomatedFlows

Whether this event type can be used in an automated flow.

Default value: False

This field is optional.

":
"{Boolean}",
7
          "name
Name

Required/mandatory field

Name of the rambase event type. This should be more human readable than eventtype.

":
"{String}",
8
          "namespace
Namespace

Namespace of the rambase event type

This field is optional.

":
"{String}",
9
          "objectDetailsUri
ObjectDetailsUri

API location for where to find more information about the object this event occurred for. May contains placeholders from with reference to parameter names. The parameter names are case sensitive.

This field is optional.

":
"{String}"
10
     }
11
}

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$showDomainDescriptions Boolean, optional Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false.
$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
<RamBaseEventType>
2
     <RamBaseEventTypeId
RamBaseEventTypeId

RamBase event type identifier

>
{Integer}</RamBaseEventTypeId>
3
     <Status
Status

Status of the Event Type

Possible domain values can be found here

>
{String}</Status>
4
     <CreatedAt
CreatedAt

Date and time of creation

>
{Datetime}</CreatedAt>
5
     <Key
Key

Key of the Event Type. This key will be used to identify which event to fire.

>
{String}</Key>
6
     <Name
Name

Name of the rambase event type. This should be more human readable than eventtype.

>
{String}</Name>
7
     <Namespace
Namespace

Namespace of the rambase event type

>
{String}</Namespace>
8
     <AllowWebhooks
AllowWebhooks

If the Event Type can be used to create webhooks

>
{Boolean}</AllowWebhooks>
9
     <AllowAutomatedFlows
AllowAutomatedFlows

Whether this event type can be used in an automated flow.

>
{Boolean}</AllowAutomatedFlows>
10
     <Description
Description

Description of the Event Type

>
{String}</Description>
11
     <ObjectDetailsUri
ObjectDetailsUri

API location for where to find more information about the object this event occurred for. May contains placeholders from with reference to parameter names. The parameter names are case sensitive.

>
12
          <Scope
Scope

Scope of the Duty

>
{String}</Scope>
13
          <IsChanged
IsChanged

Tells whether this object has been changed locally and are ready to be committed to the Repository

>
{Boolean}</IsChanged>
14
          <ChangedBy
ChangedBy

EmployeeId of the employee making the change

>
15
               <UserId
UserId

User identifier

>
{Integer}</UserId>
16
               <UserLink
UserLink

User reference

>
{String}</UserLink>
17
          </ChangedBy>
18
          <IsPendingDeployment
IsPendingDeployment

Tells whether this object has been changed locally and is ready to be deployed from the Repository

>
{Boolean}</IsPendingDeployment>
19
     </ObjectDetailsUri>
20
</RamBaseEventType>
1
{
2
     "ramBaseEventType": {
3
          "ramBaseEventTypeId
RamBaseEventTypeId

RamBase event type identifier

":
"{Integer}",
4
          "status
Status

Status of the Event Type

Possible domain values can be found here

":
"{String}",
5
          "createdAt
CreatedAt

Date and time of creation

":
"{Datetime}",
6
          "key
Key

Key of the Event Type. This key will be used to identify which event to fire.

":
"{String}",
7
          "name
Name

Name of the rambase event type. This should be more human readable than eventtype.

":
"{String}",
8
          "namespace
Namespace

Namespace of the rambase event type

":
"{String}",
9
          "allowWebhooks
AllowWebhooks

If the Event Type can be used to create webhooks

":
"{Boolean}",
10
          "allowAutomatedFlows
AllowAutomatedFlows

Whether this event type can be used in an automated flow.

":
"{Boolean}",
11
          "description
Description

Description of the Event Type

":
"{String}",
12
          "objectDetailsUri
ObjectDetailsUri

API location for where to find more information about the object this event occurred for. May contains placeholders from with reference to parameter names. The parameter names are case sensitive.

":
{
13
               "scope
Scope

Scope of the Duty

":
"{String}",
14
               "isChanged
IsChanged

Tells whether this object has been changed locally and are ready to be committed to the Repository

":
"{Boolean}",
15
               "changedBy
ChangedBy

EmployeeId of the employee making the change

":
{
16
                    "userId
UserId

User identifier

":
"{Integer}",
17
                    "userLink
UserLink

User reference

":
"{String}"
18
               },
19
               "isPendingDeployment
IsPendingDeployment

Tells whether this object has been changed locally and is ready to be deployed from the Repository

":
"{Boolean}"
20
          }
21
     }
22
}

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 102559 HTTP 400 It not allowed to update in this status
Error 102560 HTTP 400 Event type can not be "blank"
Error 102561 HTTP 400 Event type already exist on another RamBase event type